Messages
Collection Object
The Messages
collection object contains one or more Message objects.
Quick Info
|
Specified
in header file: |
MDISP.ODL |
|
First
available in version: |
OLE
Messaging Library 1.0 |
|
Parent
objects: |
Folder
(Inbox or Outbox) |
|
Child
objects: |
Message |
|
Default
property: |
Item |
A Messages collection
is considered a large collection, which means that the Count and Item
properties have limited validity, and your best option is to use a Message
object identifier value or the Get methods to access an individual
Message object within the collection.
Properties
|
|
Available
in version |
|
|
|
Application |
1.0 |
String |
Read-only |
|
Class |
1.0 |
Long |
Read-only |
|
Count |
1.1 |
Long |
Read-only |
|
Filter |
1.1 |
MessageFilter
object |
Read/write |
|
Item |
1.1 |
Message
object |
Read-only |
|
Parent |
1.0 |
Inbox or
Outbox folder object |
Read-only |
|
Session |
1.0 |
Session
object |
Read-only |
Methods
|
|
Available
in version |
|
|
Add |
1.0 |
(optional)
subject as String, |
|
Delete |
1.0 |
(none) |
|
GetFirst |
1.0 |
(optional)
filter as String |
|
GetLast |
1.0 |
(optional)
filter as String |
|
GetNext |
1.0 |
(none) |
|
GetPrevious |
1.0 |
(none) |
|
Sort |
1.0 |
sortOrder
as Long |
Remarks
The
collection does not maintain a count of the number of Message objects in the
collection. Use the GetFirst, GetLast, GetNext, and
GetPrevious methods to access the Message objects in the collection.
The order in
which items are returned by GetFirst, GetNext, GetPrevious,
and GetLast depends on whether the messages are sorted or not. The
Message objects within a collection can be sorted by delivery time, either
ascending or descending.
When the
items are unsorted, these methods do not return the items in any specified
order. The best programming approach to use with unsorted collections is to
assume that you can access all items within the collection, but that the order
of the objects is undefined.
See Also
Object
Collections